Control system and authentication device

ABSTRACT

Provided are a control system and an authentication device capable of detecting abnormality of a development device for distributing a control program and of preventing destruction and tampering of the program caused by the abnormality. To solve the above problem, there is provided: a control device that controls a controlled object; a development device that manages a plurality of control programs executed by the control device and sends the predetermined control program and information accompanying the control program to the network; and an authentication device having an authentication list storing the information accompanying the control program in association with the control program. Upon receiving the control program and the information accompanying the control program from the development device, the authentication device performs authentication whether or not the development device is normal by checking the accompanying information received from the development device with the information stored in the authentication list.

TECHNICAL FIELD

The present invention relates to a device that performs authenticationof a control program executed on a control device, and a control systemincluding such device.

BACKGROUND ART

To ensure safe and stable operation of controlled equipment such as aplant, it is necessary to ensure that a control program executed on acontrol device has been created in an appropriate environment and thatthe control program has not been destroyed or tampered before executionthereof.

As a background art related to this technical field, in PTL 1, it isdescribed that “the present invention provides safe and secureapplication distribution and execution by providing systems and methodsthat test an application to ensure that it satisfies predeterminedcriteria associated with the environment in which it will execute.Furthermore, by using rules and permission lists, application removal,and a modification detection technique, such as digital signatures, thepresent invention provides mechanisms to safely distribute and executetested, or untested, applications by determining whether the applicationhas been modified, determining if it has permission to execute in agiven wireless device environment, and removing the application.”

CITATION LIST Patent Literature

PTL 1: Japanese Unexamined Patent Publication No. 2007-293678

SUMMARY OF INVENTION Technical Problem

In a control system, a control program may be distributed to a controldevice from a general-purpose computer (hereinafter, referred to as adevelopment device) such as a PC and a server installed with adevelopment environment of the control program. In such configuration,when a software element such as an OS installed in the developmentdevice or a communication protocol driven thereby is used by a maliciousoutsider, there is a possibility that a malfunction occurs in thedevelopment device.

In PTL 1, it is disclosed that the developer can detect tampering of aprogram by using a digital signature when registering an application toa server. The digital signature, however, only indicates that theapplication to be registered has not been changed since it is out of thedeveloper's hands, whereby it is not effective in a case where amalfunction occurs to the development device itself, which is a problemto be solved by the present invention. This is because in a case wherethe control program itself in the development device has been destroyedbefore generation of the signature, for example, the digital signatureis generated for the destroyed control program, and the digitalsignature determines the destroyed control program as valid.

Accordingly, an objective of the present invention is to provide acontrol system and an authentication device capable of detectingabnormality of the development device itself that distributes thecontrol program and capable of preventing destruction and tampering ofthe program caused by the abnormality.

Solution to Problem

To solve the above-described problem, for example, a configurationaccording to claims is employed.

The present application includes a plurality of means to solve theabove-described problem, and an example thereof includes: a controldevice configured to control a controlled object; a development deviceconfigured to manage a plurality of control programs executed by thecontrol device and to send the predetermined control program andinformation accompanying the control program to a network; and anauthentication device having an authentication list in which theinformation accompanying the control program is stored in associationwith each of the control programs, the authentication device beingconfigured to perform authentication whether or not the developmentdevice is normal when receiving the control program and the informationaccompanying the control program from the development device by checkingthe accompanying information received from the development device withinformation stored in the authentication list.

Advantageous Effects of Invention

According to the present invention, it is possible to detect theabnormality of the development device itself that distributes thecontrol program and to prevent the destruction and the tampering of theprogram caused by the abnormality.

Problems, configurations, and effects other than the above-describedones are clarified in a description of embodiments below.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating an exemplary overall configuration of acontrol system according to an example of the present application.

FIG. 2 is a diagram illustrating an exemplary configuration ofidentification information according to an example of the presentapplication.

FIG. 3 is a diagram illustrating a method of generating a signatureaccording to an example of the present application.

FIG. 4 is a diagram illustrating a method of verifying a signatureaccording to an example of the present application.

FIG. 5 is a diagram illustrating an exemplary configuration of a programstorage unit according to an example of the present application.

FIG. 6 is a table illustrating an exemplary configuration of anauthentication list according to an example of the present application.

FIG. 7 is a chart illustrating a processing flow of a development deviceaccording to an example of the present application.

FIG. 8 is a chart illustrating a processing flow of an authenticationdevice according to an example of the present application.

FIG. 9 is a chart illustrating a processing flow of a control deviceaccording to an example of the present application.

DESCRIPTION OF EMBODIMENTS

Hereinafter, an example of the present invention is described by usingthe drawings.

First Example

In this example, a control system according to a first embodiment of thepresent application is described.

<Description of a Function and Operation of Each Unit>

FIG. 1 is an overall configuration diagram of the control system of thisexample.

The control system of this example includes: a controlled equipment 2constituted of various measurement devices, an actuator, and the like; acontrol device 1 that controls the controlled equipment 2; a developmentdevice 20 that distributes a control program executed by the controldevice 1; and an authentication device 30 that checks soundness of thedevelopment device 20 and creates a signature for the control program tobe distributed. The control device 1, the development device 20, and theauthentication device 30 are connected through a network 65. The controldevice 1 includes: a memory 10 that stores a control program 11; aprocessor 12 that executes the control program 11; a signatureverification unit 13 that verifies whether or not the signature that hasbeen sent from the authentication device is correct; and a signaturestorage unit 14 that stores a signature key for creating the signature.These units are mutually connected with a bus. In the control device 1,the control program 11 loaded to the memory 10 is executed by theprocessor 12, whereby a control command value for the controlled device2 is calculated. The signature verification unit 14 verifies that thecontrol program 11 to be executed is not changed based on the signaturecorresponding to the control program and a signature key 40 stored inthe signature key storage unit 14, and a result thereof is output as achange detection determination 15 (details of the signature verificationunit 14 is described later). The processor 12 refers to the changedetection determination 15 when starting execution of the controlprogram 11 and starts the execution of the control program only in acase where a change is not detected.

In this example, the memory 10 and the signature storage unit 14 areprovided as different storage devices. Accordingly, even in a case wherethere is a change to the memory 10, it is possible to securely determinesoundness of the control program by using the signature in the signaturestorage unit 14. Furthermore, in this example, a signature verificationunit 25 is provided to the processor 12 as a processing unit specializedin signature verification apart from processing. Accordingly, it ispossible to perform the signature verification without increasing aprocessing load on the processor 12.

The development device 20 includes: a human-machine interface (HMI) 65constituted of an input device such as a keyboard, a mouse, and a touchpanel as well as an output device such as a display and a speaker, a CPU61, and a memory 62. These units are mutually connected with a bus. TheCPU 61 has a program generation control unit 21 that generates thecontrol program as processing to be executed, and the memory 62 has aprogram storage unit 23 in which the control program 11 is stored, andidentification information 25, which is information accompanying thecontrol program 11, is stored in the memory 62. The development device20 provides a user with a function of creating and accumulating thecontrol program 11. The program generation control unit 21 receives asource code creation operation and an execution format programgeneration operation 22 from the source code by the user, and thecontrol program 11 is output as a product. The generated control program11 is accumulated in the program storage unit 23.

The authentication device 30 is constituted of a CPU 63, a memory 64,and a signature key storage unit 35 that stores a signature key forgenerating a signature. These units are mutually connected with a bus.The CPU 63 includes: an authentication processing unit 31 thatauthenticates soundness of the development device 20 as processing to beexecuted; and a signature generation unit 34 that generates a signaturefor the control program 11. In the memory 64, an authentication list 32used for authentication of the authentication processing unit 31 isstored. In the authentication device 30, the authentication processingunit 31 verifies the identification information 25 presented by thedevelopment device 20 by using the authentication list 32, and asignature generation permission determination 33 is output. Thesignature generation unit 34 refers to the control program 11, which isoutput from the development device 20, and the authentication key 40stored in the authentication key storage unit 35, and a signature 36corresponding to the control program is generated (details of thesignature generation unit 34 are described later).

Note that the same signature key 40 is stored in advance in thesignature key storage unit 35 of the authentication device 30 and thesignature key storage unit 14 of the control device 1. In this storingprocessing, the signature key 40 may be directly stored in each of thedevices or stored through the network 65.

<Authentication of the Program>

Next, authentication of the control program is described.

In a case where a malfunction or takeover occurs to the developmentdevice 20 caused by a malicious outsider, it is not possible to ensurevalidity of the control program 11 generated by the development device20 in the first place. Thus, first, it is necessary to confirm that thecontrol program 11 has been created in a sound environment byauthenticating the development device 20 by the authentication device30.

In this example, an example is described in which the authentication isperformed by using information that is difficult to be reproduced in acase where the malfunction or the takeover occurs to the developmentdevice 20.

First, when loading the created control program 11 to the control device1, the user gives a program registration instruction 24 to the programgeneration control unit 21. This operation is performed through the HMI65, and more specifically, it is executed by using the input device suchas the keyboard, the mouse, and the touch panel. At this time, the userinputs an instance identifier 110, which is information for identifyingthe control program 11 to be loaded, and a device identifier (alsocalled an ID, an address, or the like) 111 of the control device 1 to bea loading destination of the control program.

When the program registration instruction 24 is input by the user,first, the program generation control unit 21 searches the controlprogram associated with the instance identifier 110, which has beeninput by the user, from the program storage unit 23. When there is acorresponding one, the program generation control unit 21 acquires thecontrol program 11, which is entity thereof, and acquires a versionnumber 112 of the control program.

FIG. 5 is a conceptual diagram illustrating a data configuration of theprogram storage unit 23. In the program storage unit 23, the controlprogram is stored in a tree-like hierarchy. The hierarchy is constitutedof an item name, a system name, a controller name, and a controlprogram. By searching information corresponding to each layer input bythe user, it is possible to extract the desired control program. Notethat the control program, which is at the lowest layer, is stored inassociation with the instance identifier 110, the device identifier 111,the version number 112, and the like.

Next, by using the instance identifier 110, the device identifier 111,and the version number 112, the program generation control unit 21generates the identification information 25, which is stored in thememory 62 and presented to the authentication processing unit 31together with the control program 11. Here, it is also possible toencrypt the control program 11 with a password. FIG. 2 is a diagramillustrating a data configuration of the identification information 25.The identification information 25 is constituted of the instanceidentifier 110, the device identifier 111, and the version number 112.In addition, it is also possible to include the password related to thecontrol program 11 and user information of a user operating thedevelopment device.

In the control system, an instance of a different control program isloaded to the control device having a different ID, and the controlprogram is version upgraded as necessary for an adjustment of a controlparameter and the like, whereby it is difficult for an outsider toaccurately reproduce the information pretending to be an authorizeduser. On the other hand, the information is known to the authorized userof a conventional control system as well, whereby it is possible todetermine whether the development device 20 is sound or not byconfirming the information.

Note that as a procedure for transmitting the identification information25 from the development device 20 to the authentication processing unit31 and for determining the identification information 25 in theauthentication processing unit 31, a challenge-response method, an S/KEYmethod, and the like known in a field of information security may beapplied.

The challenge-response method is an authentication method between aserver and a client, each having a common password. It is the method ofauthenticating in which the server sends a random number to the client,the client returns the random number encrypted with the password held bythe client to the server, and the server checks the returned informationwith the random number, which is sent by the server and encrypted withthe password held by the server, and verifies whether or not these matchwith each other. Accordingly, it is possible to perform theauthentication by avoiding the password from flowing in a communicationpath as it is.

The S/KEY method is also an authentication method between a server and aclient, each having a common password. It is the method ofauthenticating in which the server sends information of the passwordthat is encrypted N fold with a hash function to the client, the clientreturns the information of the password that is encrypted N−1 fold, andthe server multiplies the received information that is encrypted N−1fold by the hash function and compares the information with theinformation that is encrypted N fold held by the server. In the sameway, by this method, it is possible to perform the authentication byavoiding the password from flowing in the communication path.

By using these methods, it is possible to avoid the identificationinformation 25 from being sent as it is in the communication pathbetween the development device 20 and the authentication device 30,whereby it is possible to prevent the identification information 25 frombeing leaked due to wiretapping and the like of the communication pathand from being abused in the authentication thereafter.

Next, processing on a side of an authentication device 31 is described.

FIG. 6 is a table illustrating a configuration of the authenticationlist 32. In the authentication list 32, user information of a usercapable of sending the program, the password, the device identifier, theversion number, and the like are stored in association with the instanceidentifier, which is identification information of the control program.

On the side of the authentication processing unit 31, the identificationinformation 25, which is presented by the development device 20, issearched from the authentication list 32. In a case where there is anentry of a matching device, the authentication processing unit 31determines that authentication is successful, and the signaturegeneration permission determination 33 is output. More specifically, byusing the instance identifier of the control program 11 sent from thedevelopment device 20 as a key, the authentication processing unit 31searches corresponding information from the authentication list 32 anddetermines whether or not the information matches with the identifier25, which is presented by the development device 20.

Furthermore, the authentication processing unit 31 outputs the signaturegeneration permission determination 33 to outside of the authenticationdevice 30 to confirm a cause in a case where execution of the controlprogram fails in the control device 1 or to confirm an operatingcondition of the authentication device. The signature generationpermission determination 33, which has been output to the outside, maybe presented to the user by a display device or may be recorded as loginformation in an external recording medium and the like.

<Generation and Verification of the Signature>

Next, generation and verification of the signature corresponding to thecontrol program 11 are described with reference to FIGS. 3 and 4.

FIG. 3 is a diagram illustrating a method of generating the signaturecorresponding to the control program 11 by the authentication device 30.

When the program registration instruction 24 is input by the user to thedevelopment device 20, the identification information 25 is presented tothe authentication device 30 as described above. At that time, thecontrol program 11 acquired from the program storage unit 23 is outputto the signature generation unit 34.

To the signature generation unit, in a case where the control program 11is input from the program storage unit 23 and the signature generationpermission determination 33 is input from the authentication processingunit 31, the signature generation unit inputs the control program 11 andthe signature key 40 stored in the signature key storage unit 35 to asignature generation algorithm 66 to generate the signature 36. As asignature generation algorithm 50, it is possible to arbitrary selectfrom a keyed hash algorithm and an encrypted hash value in which outputof a hash algorithm is encrypted that are known in the field ofinformation security as well as an algorithm designed for a similarpurpose. The signature generation unit 34 sends the signature 36generated as above to the control device 1 together with the controlprogram 11.

The control device 1 captures the control program 11 and the signature36 from the signature generation unit 34, which are loaded to the memory10. At this time, an address to which they are loaded is recorded, forexample, as additional information in a case where the control program11 is sent as a file and is referenced during loading to the memory 10.

By using the control program 11 and the signature 36 loaded to thememory 10, the signature verification unit 13 verifies whether or notthe control program 11 has been changed.

FIG. 4 is a diagram illustrating a method of verifying the controlprogram 1 in the control device 1.

First, the control program 11 in the memory 10 and the signature key 40stored in the signature key storage unit 14 are input to the signaturegeneration algorithm 50. Here, the signature algorithm 50 is the same asthe signature algorithm 66 of the authentication device 63. Although notillustrated, in actuality, a procedure is taken in which the processor12 reads the control program 11 and the signature key 40, which areinput to the signature generation algorithm 50 (the same applieshereafter). The signature generation algorithm 50 outputs a testsignature 51 as a calculation result. Next, the processor 12 inputs thetest signature 51 and the signature 36 to a comparison unit 52, and achange detection determination output 15 corresponding to a comparisonresult is output to the processor 12. When the test signature 51 matcheswith the signature 36, it is determined that there is no change to thecontrol program 11, whereby execution of the control program 11 by theprocessor 12 is permitted. On the other hand, when the test signature 51does not match with the signature 36, it is determined that there is achange to the control program 11, whereby a predetermined warning 53 isoutput.

FIG. 7 is a processing flowchart illustrating a flow of processing ofthe development device 20. The development device 20 waits untilreceiving a registration instruction of the program from the user (NO inS101), and upon receiving the registration instruction (YES in S101),the development device 20 extracts the specified control program 11 fromthe program storage unit 23 (S102). Next, the development device 20generates the identification information 25 from the control program 11that has been extracted (S103), and it sends the identificationinformation 25 and the control program 11 to the authentication device30 (S104).

FIG. 8 is a processing flowchart illustrating a flow of processing ofthe authentication device 30. The authentication device 30 waits untilthe identification information 25 is presented by the development device20 (NO in S201), and upon being presented with the identificationinformation (YES in S201), the authentication device 30 performsdetermination processing of the above-described identificationinformation (S202). In a case where authentication is not performedcorrectly as a result of the identification information determinationprocessing (NO in S203), error processing is performed (S206). In a casewhere the authentication is performed correctly (YES in S203), theauthentication device 30 generates the control program 11, and thesignature 36 from the signature key 40 (S204). Next, the authenticationdevice 30 sends the signature 36 and the control program 11 to thecontrol device 1 (S205).

FIG. 9 is a processing flowchart illustrating a flow of processing ofthe control device 1. The control device 1 waits until receiving thecontrol program 11 from the authentication device 30 (NO in S301), andupon receiving the control program 11 (YES in S301), the control device1 generates a signature by using the control program 11 that has beenreceived and the signature key 40 stored in the signature key storageunit 14 (S302). Next, the signature generated by the signatureverification unit 13 and the signature 36 sent from the authenticationdevice 30 are checked (S303). In a case where the signatures do notmatch with each other as a result of checking (NO in S304), errorprocessing is performed (S306). In a case where the signatures matchwith each other as the result of checking (YES in S304), the controldevice 1 determines that the control program 11 that has been sent isnormal and executes the program.

According to the above-described operation, in the control systemaccording to this example, the authentication device receives thecontrol program created by the development device and generates thesignature corresponding to the control program only in a case where theidentification information indicating that the development device issound is presented. By performing verification using the controlprogram, which has been loaded from the authentication device, and thesignature, which has been generated in the above-described procedure,for the control program in the control device, it becomes possible toverify that the control program has been created in a sound environmentwithout a malfunction or takeover and that the control program has notbeen changed prior to loading to the control device. Accordingly, it ispossible to prevent the control program that has been destroyed ortampered by a malfunction or takeover of the development device frombeing falsely recognized as authentic and being distributed to andexecuted on the control device. Note that as a modification of thisexample, a configuration in which, instead of the control device 1loading the control program 11 from the authentication device 30, thecontrol device 1 loads the control program 11 from the developmentdevice 20 is also possible. According to the modification, the controlprogram 11 and the signature 36 therefor exist on completely differentdevices, whereby unless both of the development device 20 and theauthentication device 30 are taken over and both of the control program11 and the signature 36 are tampered, the tampered control program 11 isnot executed on the control device 1, whereby it is possible to furtherenhance security.

Note that the CPU and the processor of the control device 1, thedevelopment device 20, and the authentication device 30 are used forforwarding a program from a nonvolatile storage medium to the memory andfor executing the program. As the program to be executed, an operatingsystem and an application program operating on the OS may beexemplified.

Furthermore, the control device 1, the development device 20, and theauthentication device 30 have a communication function with the network65. This communication function includes receiving a communicationrequest from the program executed by the CPU and the processor as wellas communicating with the network 65. As the communication function, anIC such as a media access control (MAC) chip, a physical layer (PHY)chip, a hybrid chip of MAC and PHY, a FPGA, a CPLD, an ASIC, and a gatearray may be exemplified. Note that such communication function may alsobe included in a chipset that controls the CPU, the processor, or aninformation channel inside a computer.

Furthermore, as the bus within the control device 1, the developmentdevice 20, and the authentication device 30, a PCI bus, an ISA bus, aPCI express bus, a system bus, and a memory bus may be exemplified.

Note that the present invention is not to be limited to theabove-described examples and may include various modifications. Forexample, the above-described examples have been described in detail soas to facilitate understanding of the present invention, whereby theexamples are not necessarily limited to ones provided with allconfigurations described. It is possible to replace apart of theconfiguration of one example with the configuration of another exampleor to add the configuration of another example to the configuration ofone example. Furthermore, addition, deletion, or replacement of anotherconfiguration is possible to a part of the configuration of each of theexamples.

A part or all of the above-described configuration, function, processingunit, processing means, and the like may also be achieved by hardwaresuch as by designing, for example, with an integrated circuit. Theabove-described configuration, function, and the like may also beachieved by software by interpreting and executing a program forachieving each function by a processor. Information such as a program, atable, a file, and the like for achieving the function may be put on asemiconductor memory, a recording device such as a hard disk, or on arecording medium using magnetic or light.

Note that only a control line and an information line considered to benecessary for describing are illustrated, and not all of the controllines and the information lines of the product are illustrated. Inactuality, it may be regarded that almost all of the configurations aremutually connected.

REFERENCE SIGNS LIST

-   1 control system-   2 controlled equipment-   10 memory-   11 control program-   12 processor-   13 signature verification unit-   14 signature key storage unit-   15 change detection determination-   20 development device-   21 program generation control unit-   22 source code creation and program generation operation-   23 program storage unit-   24 program output instruction-   25 identification information-   30 authentication device-   31 authentication processing unit-   32 authentication criteria information-   33 signature generation permission determination-   34 signature generation unit-   35 signature key storage unit-   40 signature key-   61 CPU-   62 memory-   63 CPU-   64 memory-   65 network-   66 signature generation algorithm

The invention claimed is:
 1. A control system comprising: a controldevice configured to control a controlled object; a development deviceconfigured to manage a plurality of control programs executed by thecontrol device and to send a control program and informationaccompanying the control program to a network; and an authenticationdevice having an authentication list in which the informationaccompanying the control program is stored in association with each ofthe control programs as authentication information for the controlprograms, the authentication device being configured to performauthentication whether or not the development device is normal whenreceiving the control program and the information accompanying thecontrol program from the development device by checking the accompanyinginformation received from the development device with the authenticationinformation for the control program stored in the authentication list;wherein the development device is normal if the accompanying informationreceived from the development device matches the authenticationinformation for the control program stored in the authentication list,and the development device is not normal if the accompanying informationreceived from the development device does not match the authenticationinformation for the control program stored in the authentication list;and wherein the information accompanying the control program comprisesidentification information generated using an instance identifier foridentifying the control program, a device identifier identifying thecontrol device to be an object, and version information of the controlprogram.
 2. The control system according to claim 1, wherein in a casewhere the development device is determined as normal as a result of theauthentication, the authentication device generates a signature from thereceived control program and sends the signature to the control device.3. The control system according to claim 2, wherein upon receiving thecontrol program from the development device or the authenticationdevice, the control device generates a signature based on the receivedcontrol program and executes the control program in a case where a matchis obtained by checking the generated signature with the signaturereceived from the authentication device.
 4. The control system accordingto claim 3, wherein a common signature key is stored in advance in theauthentication device and the control device, and each of theauthentication device and the control device generates a signature fromthe control program by using the signature key stored therein.
 5. Thecontrol system according to claim 1, wherein the informationaccompanying the control program further comprises a password.
 6. Anauthentication device connected to a control device configured tocontrol a controlled object and to a development device configured togenerate a control program through a network, the authentication devicecomprising: a memory configured to store an authentication list in whichinformation accompanying the control program is associated with each ofthe control programs as authentication information for the controlprograms; and an authentication processing unit configured to performauthentication whether or not the development device is normal uponreceiving the control program generated by the development device andthe information accompanying the control program through the network bysearching whether or not the accompanying information received from thedevelopment device matches the authentication information for thecontrol program stored in the authentication list, to generate asignature from the control program that has been received in a casewhere the development device is determined as normal, and to send thesignature to the control device; wherein the development device isnormal if the accompanying information received from the developmentdevice matches the authentication information for the control programstored in the authentication list, and the development device is notnormal if the accompanying information received from the developmentdevice does not match the authentication information for the controlprogram stored in the authentication list; and wherein the informationaccompanying the control program comprises identification informationgenerated using an instance identifier for identifying the controlprogram, a device identifier identifying the control device to be anobject, and version information of the control program.
 7. Theauthentication device according to claim 6, wherein in a case where thedevelopment device is determined as normal as a result of theauthentication, the authentication processing unit generates a signaturefrom the received control program and sends the signature to the controldevice.
 8. The authentication device according to claim 7, wherein acommon signature key is stored in advance in the authentication deviceand the control device, and the authentication device generates asignature from the control program by using the signature key storedtherein.
 9. The authentication device according to claim 6, wherein theinformation accompanying the control program further comprises apassword.
 10. The control system according to claim 3, wherein thecontrol device executes the control program to control the controlledobject in the case where a match is obtained by checking the generatedsignature with the signature received from the authentication device.11. A control method for a control system that includes a control deviceconfigured to control a controlled object, a development deviceconfigured to manage a plurality of control programs executed by thecontrol device and to send a control program and informationaccompanying the control program to a network, and an authenticationdevice having an authentication list in which the informationaccompanying the control program is stored in association with each ofthe control programs as authentication information for the controlprograms, the control method comprising: performing, by theauthentication device, authentication whether or not the developmentdevice is normal when receiving the control program and the informationaccompanying the control program from the development device by checkingthe accompanying information received from the development device withthe authentication information for the control program stored in theauthentication list; wherein the development device is normal if theaccompanying information received from the development device matchesthe authentication information for the control program stored in theauthentication list, and the development device is not normal if theaccompanying information received from the development device does notmatch the authentication information for the control program stored inthe authentication list; and wherein the information accompanying thecontrol program comprises identification information generated using aninstance identifier for identifying the control program, a deviceidentifier identifying the control device to be an object, and versioninformation of the control program.
 12. The control method according toclaim 11, further comprising: in a case where the development device isdetermined as normal as a result of the authentication, generating, bythe authentication device, a signature from the received control programand sending the signature to the control device.
 13. The control methodaccording to claim 12, further comprising: upon receiving the controlprogram from the development device or the authentication device,generating, by the control device, a signature based on the receivedcontrol program and executing the control program in a case where amatch is obtained by checking the generated signature with the signaturereceived from the authentication device.
 14. The control methodaccording to claim 13, further comprising: storing a common signaturekey in advance in the authentication device and the control device,wherein each of the authentication device and the control devicegenerates a signature from the control program by using the signaturekey stored therein.
 15. The control method according to claim 13,wherein the control device executes the control program to control thecontrolled object in the case where a match is obtained by checking thegenerated signature with the signature received from the authenticationdevice.
 16. The control method according to claim 11, wherein theinformation accompanying the control program further comprises apassword.